-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: only include required networks for e2e tests #2149
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
…e into fix-e2e-ci-no-list
…e into fix-e2e-ci-no-list
…e into fix-e2e-ci-no-list
…e into fix-e2e-ci-no-list
…e into fix-e2e-ci-no-list
…e into fix-e2e-ci-no-list
@@ -16,5 +16,8 @@ export function shortenTxHash(txHash: string) { | |||
)}` | |||
} | |||
|
|||
export const isE2eTestingEnvironment = | |||
typeof window !== 'undefined' && !!window.Cypress | |||
|
|||
export const isTestingEnvironment = |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's 2 places where we use isTestingEnvironment
:
- in
ProjectListing.tsx
to display some dummy data - in
setup.ts
to configure chains
I think what we really need is isDevelopmentEnvironment
because both of these use cases really depend on that. Having both isE2eTestingEnvironment
and isTestingEnvironment
is confusing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, good name isDevelopmentEnvironment
! Even I felt having isE2eTestingEnvironment
and isTestingEnvironment
was not optimal but couldn't come up with the perfect naming. Ty!
Closes FS-1070